Skip to content

docs(site): give a search result and a shared link a title and a picture - #36

Merged
danielvogler merged 3 commits into
feat/terminal-commandsfrom
docs/findable
Nov 19, 2026
Merged

danielvogler merged 3 commits into
feat/terminal-commandsfrom
docs/findable

Conversation

@faviens-agent-daniel

Copy link
Copy Markdown
Contributor

Stacked on the pull request for the terminal commands: this branch starts from that one, since the new shell-loop page is linked here.

What changes for a user

  1. Every page of the documentation site has a title that says what it is about ("The board: a local dashboard for agent loops", not "The board"), Open Graph and card tags, and a card picture; the first page also describes the project as structured data.
  2. The site loads no font from another host.
  3. A page of questions and answers: what an agent loop is, how to monitor, stop and steer one, which agents work, what leaves the machine.
  4. The command reference describes every argument, keeps proper names as written and lists the events emit takes; the MCP reference and the standard no longer say "door".
  5. A release note prints up to six bullets of its commit below the subject, so a release says why as well as what.

Why

A shared link showed the host's generic card, a search result showed two-word titles, and the site asked another host for its fonts while the board vendors its own and loads nothing from anywhere. The ledger held each of these, with the empty descriptions of the command reference, the word nobody outside the project knows, and release notes of one line per change.

Done when

  • A test fails without this change, and make check is green (699 tests).
  • Looked at for real: the site was built and its pages read for their titles, card tags and structured data, and for the absence of the font host; the card picture was rendered at 1200 by 630. The published site, a link pasted into a chat and the notes of a real release are listed in .agent/DEFERRED_VERIFICATION.md.
  • Text, models and schema of the standard agree (make schema), if the protocol changed. One sentence of the standard was reworded; no field or event changed.
  • feat, fix and perf subjects read as lines of release notes; a decision has its section in docs/ARCHITECTURE.md. No new decision.
  • Nothing names a company, a client or a real loop. The questions page names agent products as examples, as the agents page does.
  • The title and this text describe the change, not the conversation that led to it.

…e and a picture

- The site's pages carried no card data, so a shared link showed the
  host's generic card, and most page titles were one or two words
  ("Setup", "The board") that say nothing in a search result. Every
  page now has a title that names what it is about, Open Graph and
  card tags, and a picture; the first page also says what the project
  is as structured data.
- The site loaded its fonts from another host, while the board vendors
  its font and loads nothing from anywhere. The site now uses the
  reader's own fonts.
- A page of questions and answers puts into words what people search
  for: what an agent loop is, how to monitor, stop and steer one, which
  agents work, what leaves the machine.
- The generated command reference had eleven arguments without a
  description, wrote "Mcp" for MCP, and did not list the events `emit`
  takes. Every argument has one now, the first letter alone is
  capitalised, and `emit` names its events.
- "Door" stood for the two ways a loop writes its files. A reader new
  to the project met it in the MCP reference and the standard with
  nothing to say what a door is. Those texts now say script, session
  and MCP server.
… notes

- A release note was one subject per commit: what changed, never why,
  though every commit says why in its bullets.
- The notes now print up to six bullets of a commit's body below its
  subject. Check boxes and text that is no bullet are left out.
@danielvogler
danielvogler merged commit 4c1a209 into feat/terminal-commands Nov 19, 2026
1 check passed
@danielvogler
danielvogler deleted the docs/findable branch November 19, 2026 16:10
danielvogler added a commit that referenced this pull request Nov 19, 2026
… its inbox (#35)

* feat(cli): show every loop in the terminal, and let a shell loop read its inbox

- What waits for a person was seen only on the board. `loopcaptain
  status` prints one line per watched loop, what needs the person
  first: status, round, last line and what the loop asks.
- A loop in shell could report with `emit` and had no way to read what
  the person sent. `loopcaptain inbox <loop>` prints it, one line each,
  and marks it read. It prints only lines the board signed for this
  loop that answer the present asking, so a script cannot take a
  forged stop by mistake; `--json` shows every entry.
- The docs gain a worked `loop.sh` for a Ralph loop, which a test runs
  as printed: it reports two rounds, hands a note to the agent and
  takes a stop.

* feat(board): tell a tab in the background that a loop waits

- A tab that is not in front was never drawn again, so the count in
  its title stayed as it was and a loop could wait unseen for hours.
- The pulse the page polls now carries how many loops wait. A tab in
  the background puts that count in its title, and shows a browser
  notification when it rises, where the person allowed one through
  the button in the footer.
- A tab that comes back in front draws what changed at once.
- Everything stays on this machine: the notification is made by the
  page's own script, and no page loads anything from another origin.

* feat(package)!: make the MCP server an extra, loopcaptain[mcp]

- The MCP SDK came with every install though only a loop driven by an
  agent session uses it: a plain install is 21 packages and 12 MB
  without it, 36 packages and 28 MB with it.
- `loopcaptain mcp` on an install without the extra ends with one line
  that names the install command, and `mcp-config` says the same
  beside the block it prints. The board, the helper, `emit`, `inbox`
  and every other command need nothing more than before.

BREAKING CHANGE: `loopcaptain mcp` needs the package installed as
`loopcaptain[mcp]`. An agent session set up against a plain install
gets the one-line message until it is reinstalled with the extra.

* docs(site): give a search result and a shared link a title and a picture (#36)

* docs(site): give a search result and a shared link a title, a sentence and a picture

- The site's pages carried no card data, so a shared link showed the
  host's generic card, and most page titles were one or two words
  ("Setup", "The board") that say nothing in a search result. Every
  page now has a title that names what it is about, Open Graph and
  card tags, and a picture; the first page also says what the project
  is as structured data.
- The site loaded its fonts from another host, while the board vendors
  its font and loads nothing from anywhere. The site now uses the
  reader's own fonts.
- A page of questions and answers puts into words what people search
  for: what an agent loop is, how to monitor, stop and steer one, which
  agents work, what leaves the machine.

* docs(cli): describe every argument, and say server where it said door

- The generated command reference had eleven arguments without a
  description, wrote "Mcp" for MCP, and did not list the events `emit`
  takes. Every argument has one now, the first letter alone is
  capitalised, and `emit` names its events.
- "Door" stood for the two ways a loop writes its files. A reader new
  to the project met it in the MCP reference and the standard with
  nothing to say what a door is. Those texts now say script, session
  and MCP server.

* feat(release): print a commit's reasons below its line of the release notes

- A release note was one subject per commit: what changed, never why,
  though every commit says why in its bullets.
- The notes now print up to six bullets of a commit's body below its
  subject. Check boxes and text that is no bullet are left out.

---------

Co-authored-by: danielvogler <danielvogler@users.noreply.github.com>

---------

Co-authored-by: danielvogler <danielvogler@users.noreply.github.com>
Co-authored-by: faviens-agent-daniel[bot] <354525062+faviens-agent-daniel[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant